View Issue Details

IDProjectCategoryView StatusLast Update
0000770T99X171.00 SKB EagleSWpublic2019-11-08 13:22
Reporter(ALTech) Jason ParkAssigned To(SW) Bcan Yeh Due Date
PrioritynormalSeveritys2-severeReproducibilityhave not tried
Status closedResolutionduplicate 
Summary0000770: [Eagle][Common] ATT Implementation
DescriptionATT implement status.

[8/21] Will include Attdaemon.apk and related framework modification into 8/23 FW build and still need to take 4~6 weeks to implement testing APK which will be stored in USB disk and receive and execute testing commands sent by ATT program running on PC
[8/28] Mr.Yoon asked to Foxconn about your plan regarding to verify ATT damon in v49? if you have comment, please leave your comment.
[FXN-8/28] We already did framework modification from FW v48 and verified it was working well.
However, we are working on developing ATTdaemon.apk now and will take one week to have 1st version with basic functionality and we may provide it to you for 1st trial.
TagsNo tags attached.
Attach Tags

Relationships

related to 0000548 closed(ALTech) Jason Park ATT - Android security violence check 

Users monitoring this issue

User List (ALTech) SY Yoon , (SW) Bcan Yeh

Activities

(SW) Bcan Yeh

2019-09-05 18:29

developer   ~0002962

Hi Mr.Park,

Below is a question from mantis 0000548.

******************************************************************************
Q6. Who should control the LED in the aging test procedure?

Foxconn:
    When should testers remove the USB disk?
    According to the item "Check USB Port" of p29, it seems that testers should remove the USB disk after installing the daemon.
    And the aging test procedure will go ahead after removing the USB disk.
    Is that correct?

ALT :
    Tester remove USB when LED blink.
    LED should be blink after deamon is installed.

Foxconn:
   According to all answers you provided before.
   Our understanding is that
     1. Insert a USB disk.
     2. Install the STB ATT Daemon.
     3. The STB starts blinking the LED after the STB ATT Daemon is installed.
     4. The tester removes the USB disk when the LED is blinking.
     5. The STB stops blinking the LED after the USB disk is removed.
     6. It goes to the next step of the ATT procedure after the USB disk is removed.
     We want to make sure that the time points and steps are correct, especially item 4/5/6.
     Are the steps above correct?

(ALTech) Jason Park

2019-09-06 10:51

developer   ~0002970

Hi Bcan

Your comment is right.

please see a step as below.

# Start from STB Power Off state
1. Connecting USB to STB
2. STB Power On
3. When STB is booted, the daemon is installed when it is recognized that there is a daemon file on the USB.
4. The daemon flashes all LEDs at 0.5 second intervals (until the user removes the USB) to inform the user when to remove the USB.
5. When the user uninstalls the USB, the daemon authenticates (including default settings and authentication window * processing), and reboots.
6. The Certification Window screen must be opened when the STB boots.
7. STB daemon sends Step information (IP, MAC, etc.) to the ATT server and waits for connection from the ATT program.
7. ATT program connects to STB daemon to initiate command delivery

(ALTech) SY Yoon

2019-09-06 11:24

developer   ~0002973

Hi Bcan Yeh,

I have question about your ATT Daemon that installed in STB.
What is the role or function of ATT Daemon in the STB.
And please update your status. When you can test it with ATT server ?

(ALTech) SY Yoon

2019-09-17 14:31

developer   ~0002998

Hi Bcan Yeh and Jacky Chiang,

I have questions about ATT as follows :
1. The role of ATT Deamon that installed in STB.
2. Your plan
    - Implentation plan : When you can provide 1st test SW to HM solution and us to test it ?
    - Debug plan : When will you test ATT with ATT server in Korea with HM Solution

(SW) Bcan Yeh

2019-09-17 17:10

developer   ~0003004

Hi Mr.Yoon,
1. AttDaemon can be updated through a USB disk.
   It will handle all the ATT procedure in page 3 of "STB ATT SystemInterconnectProtocol_v7.0".
   It is also the STB Daemon itself.
2. We will provide an AttDaemon.apk for testing on 9/25.

(ALTech) SY Yoon

2019-09-17 18:26

developer   ~0003006

Hi Mr. Bcan Yeh,

Could you inform which files are in USB disk for ATT ?
Please let me know the list of files in USB disk.
And I think Foxconn engineer should be came to Korea to test ATT.
Please let me know Foxconn engineer will visit korea when you release SW.

(SW) Bcan Yeh

2019-09-19 15:19

developer   ~0003027

Last edited: 2019-09-19 15:36

Hi Mr.Yoon,

Could you inform which files are in USB disk for ATT ?
=> 1. There should be a directory _BFX_Att_Data_ in the USB disk.
   2. _BFX_Att_Data_/ServerURL.txt for the URL of the ManagementServer.
   3. _BFX_Att_Data_/AttDaemon.apk for updating AttDaemon.


I have some questions about key mapping.

Below is the key list in page 14 of "STB ATT SystemInterconnectProtocol_v7.0.pptx".
I tried to map all the buttons of RCU to the key list.
1. Should I map HWM_KEY_CANCEL to BACK(AndoridKeyCode 4) ?
2. In the STBCommunicationTester, there are some keys those I can't find corresponding buttons on the RCU.
  - 1C(HWM_KEY_SEARCH)
  - 2B(even not found in the list)
  Will these two key codes be used in the practical ATT procedure?

ps. Please check keyMapping.png for the detail of key list.

(SW) Bcan Yeh

2019-09-19 15:34

developer  

keyMapping.png (61,935 bytes)   
keyMapping.png (61,935 bytes)   

(ALTech) SY Yoon

2019-09-19 17:48

developer   ~0003032

Hi Bcan Yeh,

I checked with HM Solution about your question.1
1. You can map HWM_KEY_CANCEL to KEYCODE_BACK(AndoridKeyCode 4).
2. You can map key code 1C in the STBCommunicationTester to KEYCODE_SEARCH(AndroidKeyCode 84).
    You can map key code 2B in the STBCommunicationTester to KEYCODE_POUND(AndroidKeyCode 18).
    BA01 RCU doesn't have KEYCODE_SEARCH. But our STB can handle KEYCODE_SEARCH from other RCU, such as BT10(RCU for AOSP).
    HM Solution said that they don't use RCU directly for ATT. They just use key code to communication between ATT server and daemon.
    So if our STB can handle KEYCODE_SEARCH, then it is OK even though our RCU doesn't have that keys.

If you have any more question, then please let me know.

(ALTech) SY Yoon

2019-09-19 20:09

developer   ~0003034

Hi Bcan Yeh,

I just got updated STB ATT SystemInterconnectProtocol_v7.2.pdf today.
So I translate and attached it.
You can see the revision history(page 2).
I think you just see th page 8.
HM Solution add Reboot before dete program and move factory reset to final stage.
Other changes is not important. They add some examples.
HM Solution said that 4.3 as a major issue, but I think they explain the sequence once more.
You don't care about it. I will check it and update it.

(ALTech) SY Yoon

2019-09-20 10:06

developer   ~0003038

Hi Bcan Yeh,

I got feedback from HM Solution about 4.3.
It is an explanation of the sequence of ATT Deamon installation.
They worried about SW upgrade when STB reboot.
You can see this step in the doc. page 5.
HM solution describe more details of "Ready to Test" Step.
4.3 explain this more detail.

Currently live network has SW v 15.502.43, but we are using SW v. 15.502.50.
So STB shows Upgrade message whenever we reboot.
To avoid this, HM solution ask us to revoke authentication.
If STB is unauthorized, then STB will wait on authentication screen after boot,
even though STB has differen version of SW.

If you download latest SW(SW v 15.502.44 or higher) and test ATT,
then you can see Upgrade menu whenever you reboot STB.

If you have any question, please let us know.

(SW) Bcan Yeh

2019-09-20 11:03

developer   ~0003039

Hi Mr.Yoon,

1. According to the update of "4.3 Major Issues" in the page 32 of "STB ATT SystemInterconnectProtocol_v7.2.pptx"
   The step 6. seems to be conflict with page 5/6/7 of the document.
   - STBDaemon needs be connected with ATT program(PC), and then STBDaemon can get CITIZEN-NUMBER/LOGIN-NUMBER for authentication.
   - Before the 'reboot' of step 6, there should be some ations (ex.'Update channels') need to be done.
   Because You mentioned that it is an explanation of the sequence of ATT Deamon installation.
   Maybe it's just some negligence about the details of whole flow.
   I will implement the flow with page 5/6/7/8 of the document.

2. Should there be a VOD-Stop after VOD-Start in the step 'Check VoD Broadcast' of page 7.
    I saw the 'VOD-Stop' command, but I can't find it in the flow.

3. We will prohibit auto-upgrade.

(ALTech) SY Yoon

2019-09-20 13:59

developer   ~0003041

Hi Mr. Bcan Yeh,

1. I talked with HM solution on your question.
     I have some misunderstandings.
     I correct it.
      "Step 6. Daemon inputs basic settings and reboot after user pulls out USB from STB.
      When Deamon input authentication code, screen show “*” instead of real number."
      =>
      "Step 6. Daemon inputs basic settings and reboot after user pulls out USB from STB.
      The basic settings are include the setting that user input authentication code with “*”,
       not real number."
       So authentication process will not run in this step 6. It just set the settings.
       I attached changed document.
2. On "VoD stop" :
     I cannot see the VoD Stop command in the flow in the document.
     HM Solution said that it also provide by STB ATT Program after VoD Start.
     HM solution will add this command later. I will share it when they release new one.
     But I think you can make SW without additional document.
     VoD stop command is already defined in the document.
     So STB start VoD stop operation when ATT Program send this command.
     Can you implement it without additional document ?

And we have question about daemon installation.
User connect USB and turn on the STB, then which one start earlier than other between ATT Daemon and Btv App ?
During the ATT Daemon installation and work, does Btv App start or not ?
I think Btv App start during deamon installation, then Btv may upgrade when it reboot.

(SW) Bcan Yeh

2019-09-20 15:52

developer   ~0003046

Hi Mr.Yoon,
1. I can implement it without additional document.
    But I still want to get the latest version ATT document.
2.
User connect USB and turn on the STB, then which one start earlier than other between ATT Daemon and Btv App ?
=> Btv App is earlier than AttDaemon.
During the ATT Daemon installation and work, does Btv App start or not ?
I think Btv App start during deamon installation, then Btv may upgrade when it reboot.
=> Yes, but AttDaemon will prohibit auto-upgrade and reboot.
     This means Btv upgrade might be shown during AttDaemon installation and "Ready to Test" step.
     But after rebooting, Btv upgrade dialog won't show again.

(SW) Bcan Yeh

2019-09-24 08:44

developer   ~0003047

Last edited: 2019-09-24 08:45

Hi Mr.Yoon,
We have some problem in blinking the led in the period of 0.5 second.
The period of blinking is 1 second now.
Is it OK to change the color of blinking instead of changing the period ?

(SW) Bcan Yeh

2019-09-24 18:29

developer   ~0003049

Hi Mr.Yoon,

https://www.hmit.co.kr/control/stbinfo_insert_test.asp?STB_MAC=001122334455&STB_IP=111.222.111.111&AUTHENTICATION=0&REBOOT_STEP=1&STB_SW_VER=1.1.1.1&STB_PARTIAL_VER=0.0.0.1&STB_MODEL=AAA-AI600&DAEMON_VER=190614

The test url of management server does not work from 9/24 afternoon.
The web page shows messages as below.
----------------------------------------------------------------------------------------------------------
An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.
----------------------------------------------------------------------------------------------------------
Please help to inform HM Solution.

(ALTech) SY Yoon

2019-09-25 09:55

developer   ~0003053

Hi Bcan Yeh,

HM solution provide real test server url as follows. :

http://att.skbroadband.com:54321/STBInfo_Insert_new2.asp
https://att.skbroadband.com/control/STBInfo_Insert_new2.asp

You can use above web site and add your parameter for test.

And on LED Blink,
They don't care the on/off time. It is okay 1sec.
But I think it may make some confusion to tester.
Is it easy to identify current step when tester see the white blink LED ?
Tester may confuse this step is boot step or ATT Deamon installation complete.
Normally tester didn't see the TV when they install ATT deamon.
So we may change color of LED to indicate ATT Deamon installation complete.
Can we change LED to Green blink when ATT Deamon installation complete ?

(SW) Bcan Yeh

2019-09-25 20:05

developer   ~0003057

Hi Mr.Yoon,

Can we change LED to Green blink when ATT Deamon installation complete ?
=> Yes, we can change the blinking light to green.

(SW) Bcan Yeh

2019-09-25 20:12

developer   ~0003058

Hi Mr.Yoon,

Here is the release of AttDaemon.
versionName: 1.0.9_2019.09.25.1730
versionCode: 2
AttDaemonRelease_1.0.9.zip (2,460,531 bytes)

(ALTech) SY Yoon

2019-09-26 09:17

developer   ~0003059

Last edited: 2019-09-26 09:34

Bcan Yeh,

I make Dir. in USB named "_BFX_Att_Data_".
And copy ServerURL.txt and AttDeamon.apk to that directory.
And plug in USB port of STB and Reboot.
Then STB reboot normally. There is no action for ATT.
Please let me know what is wrong in my work.
I use SW V15.502.51 SU version.
Do I change something in settings ?

Did you test it with ATT server ?
And can you test ATT test without help to HM solution ?
Please let us know your test result.

(SW) Bcan Yeh

2019-09-26 09:46

developer   ~0003060

Hi Mr.Yoon,

Did you test it with ATT server ?
=> STB Daemon(AttDaemon) have to cooperate with ATT Server and STB ATT Program (PC).
     ATT Server: https://att.skbroadband.com/control/STBInfo_Insert_new2.asp (As you said, it is the real test server url. )
     STB ATT Program (PC): STBCommunicationTester.exe (It's a simulator of actual STB ATT Program.)
     I used the above to complete AttDaemon test.

And can you test ATT test without help to HM solution ?
=> My test is just a kind of simulation. It still need to be tested in the practical environment.

Please let us know your test result.
=> The whole ATT procedure runs well in the simulation.

(ALTech) SY Yoon

2019-09-26 12:50

developer   ~0003062

Hi, Mr. Bcan Yeh,

I plugged in USB to our STB and Boot up.
But it works normal STB.
Is there any precess or work to do before start ATT Test ?
Why I cannot install ATT Deamon in USB ?
Please advice me.

(SW) Bcan Yeh

2019-09-26 18:52

developer   ~0003063

ATT Program simulator

(ALTech) Jason Park

2019-10-15 13:28

developer   ~0003095

hi bcan

 Mr.Yoon already sent to you at 10/11.
 I copy it here. and I open it again. please check this.
 I checked ATT Daemon after 24 hours from the installation.
 There is no below 2 files.
            AttRebootFlag
            AttTimeStamp

 Does ATTDaemon remove above 2 files when STB reboot ?
 And please answer below questions

 HM Solution said that if ATT Daemon exists in the STB, then it may use CPU load.
 Some SKB STB worked like this. So SKB checked it and remove Daemon App in the STB.
 But if our STB doesn’t have above 2 files in btv_home, then doesn’t ATTDaemon App work ? Does it mean that ATTDaemon doesn’t use CPU ?

(ALTech) Jason Park

2019-11-08 13:22

developer   ~0003186

hi bcan

Mr.Yoon talked with you through mantis 548 about this.
so i'm close this.

Thanks.

Issue History

Date Modified Username Field Change
2019-08-30 16:25 (ALTech) Jason Park New Issue
2019-09-04 17:13 (SW) Bcan Yeh Issue Monitored: (SW) Bcan Yeh
2019-09-05 14:21 (SW) Jacky Chiang Assigned To => (SW) Bcan Yeh
2019-09-05 14:21 (SW) Jacky Chiang Status new => assigned
2019-09-05 18:29 (SW) Bcan Yeh Note Added: 0002962
2019-09-05 19:47 (SW) Bcan Yeh Assigned To (SW) Bcan Yeh => (ALTech) Juyoung Park
2019-09-05 19:48 (SW) Bcan Yeh Assigned To (ALTech) Juyoung Park => (ALTech) Jason Park
2019-09-06 10:51 (ALTech) Jason Park Note Added: 0002970
2019-09-06 11:19 (ALTech) SY Yoon Issue Monitored: (ALTech) SY Yoon
2019-09-06 11:20 (ALTech) SY Yoon Assigned To (ALTech) Jason Park => (SW) Bcan Yeh
2019-09-06 11:24 (ALTech) SY Yoon Note Added: 0002973
2019-09-17 14:31 (ALTech) SY Yoon Note Added: 0002998
2019-09-17 17:10 (SW) Bcan Yeh Note Added: 0003004
2019-09-17 18:26 (ALTech) SY Yoon Note Added: 0003006
2019-09-19 15:19 (SW) Bcan Yeh Note Added: 0003027
2019-09-19 15:34 (SW) Bcan Yeh File Added: keyMapping.png
2019-09-19 15:36 (SW) Bcan Yeh Note Edited: 0003027
2019-09-19 15:37 (SW) Bcan Yeh Assigned To (SW) Bcan Yeh => (ALTech) SY Yoon
2019-09-19 17:48 (ALTech) SY Yoon Note Added: 0003032
2019-09-19 20:09 (ALTech) SY Yoon File Added: STB ATT SystemInterconnectProtocol_v7.2.pptx
2019-09-19 20:09 (ALTech) SY Yoon Note Added: 0003034
2019-09-19 20:10 (ALTech) SY Yoon Assigned To (ALTech) SY Yoon => (SW) Bcan Yeh
2019-09-20 10:06 (ALTech) SY Yoon Note Added: 0003038
2019-09-20 11:03 (SW) Bcan Yeh Note Added: 0003039
2019-09-20 11:03 (SW) Bcan Yeh Assigned To (SW) Bcan Yeh => (ALTech) SY Yoon
2019-09-20 13:59 (ALTech) SY Yoon File Added: STB ATT SystemInterconnectProtocol_v7.2-2.pptx
2019-09-20 13:59 (ALTech) SY Yoon Note Added: 0003041
2019-09-20 15:52 (SW) Bcan Yeh Note Added: 0003046
2019-09-24 08:44 (SW) Bcan Yeh Note Added: 0003047
2019-09-24 08:45 (SW) Bcan Yeh Note Edited: 0003047
2019-09-24 18:29 (SW) Bcan Yeh Note Added: 0003049
2019-09-25 09:55 (ALTech) SY Yoon Note Added: 0003053
2019-09-25 09:56 (ALTech) SY Yoon Assigned To (ALTech) SY Yoon => (SW) Bcan Yeh
2019-09-25 20:05 (SW) Bcan Yeh Note Added: 0003057
2019-09-25 20:12 (SW) Bcan Yeh File Added: AttDaemonRelease_1.0.9.zip
2019-09-25 20:12 (SW) Bcan Yeh Note Added: 0003058
2019-09-25 20:12 (SW) Bcan Yeh Assigned To (SW) Bcan Yeh => (ALTech) SY Yoon
2019-09-26 09:17 (ALTech) SY Yoon Note Added: 0003059
2019-09-26 09:34 (ALTech) SY Yoon Note Edited: 0003059
2019-09-26 09:35 (ALTech) SY Yoon Assigned To (ALTech) SY Yoon => (SW) Bcan Yeh
2019-09-26 09:46 (SW) Bcan Yeh Note Added: 0003060
2019-09-26 12:50 (ALTech) SY Yoon Note Added: 0003062
2019-09-26 18:52 (SW) Bcan Yeh File Added: STB ATT 프로토콜 테스트.zip
2019-09-26 18:52 (SW) Bcan Yeh Note Added: 0003063
2019-09-27 14:48 (ALTech) Jason Park Relationship added related to 0000548
2019-10-15 13:28 (ALTech) Jason Park Note Added: 0003095
2019-11-08 13:22 (ALTech) Jason Park Note Added: 0003186
2019-11-08 13:22 (ALTech) Jason Park Status assigned => closed
2019-11-08 13:22 (ALTech) Jason Park Resolution open => duplicate